One of the most widely used models for specifying functional requirements is a use case\nmodel. The viewpoint of the use case model that views a system as a black box focuses on descriptions\nof external interactions between the system and related environments. However, for embedded\nsystems that do not disclose most implementation logics outside the system, black box-based use case\nmodels may experience the drawback that considerable information that must be defined for system\ndevelopments is omitted. To solve this shortcoming, several studies have been proposed on the use\nof kind of white box technique in which the dynamic behaviors of embedded systems are defined\nfirst using a state diagram and the results are reflected in the requirement specifications. However,\nwhite box-based modeling has not been widely adopted by developers due to tasks that require a lot\nof time in the requirement analysis phase in the initial phase of the software development life cycle.\nThis study proposes a gray box-based requirement specification method as a trade-off between two\ncontradictory elements (the amount of information required to develop an embedded system and the\ncost of the effort required during the requirement analysis phase) in terms of the two approaches, the\nblack and the white box-based models. The proposed method suggests that an appropriate depth\nlevel of embedded system modeling is required to define the requirements. This study also proposes\na mechanism that automatically generates an application programming interface for each component\nbased on the created model. The proposed method was applied to the development of a camera\nsensor controller in a mobile phone, and the case results proved the feasibility of the method through\ndiscussion of the application results.
Loading....